[process-reboot-cause] Save boot_id and device fields for DPU reboot cause#405
[process-reboot-cause] Save boot_id and device fields for DPU reboot cause#405chartsai-nvidia wants to merge 2 commits into
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Hi, there are workflow run(s) waiting for approval, you may be first-time contributor. I will notify maintainers to help approve once PR is approved. Thanks! ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
12 similar comments
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
|
This PR has backport request label(s) for branch(es): 202605, but is missing required test information. Please make sure you tick the tested branch(es) in the Tested branch section and provide test evidence (e.g., 202605: <test result>) in the Test result section as well in your PR description. ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
1 similar comment
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
|
Hi @sonic-net/sonic-host-services-maintainer, this approved PR has workflow run(s) waiting for approval. Please help review. Thanks! ---Powered by SONiC BuildBot
|
vvolam
left a comment
There was a problem hiding this comment.
Thanks for the cleanup — the loop-over-field-set refactor is clear and backward-compatible (NPU rows keep exactly cause/time/user/comment). One correctness gap inline regarding the device field, plus an optional nit below.
Nit (optional): to keep the two tuples from drifting, consider deriving one from the other:
NPU_REBOOT_CAUSE_DB_FIELDS = ("cause", "time", "user", "comment")
DPU_REBOOT_CAUSE_DB_FIELDS = NPU_REBOOT_CAUSE_DB_FIELDS + ("boot_id", "device")Signed-off-by: Charles Tsai <chartsai@nvidia.com>
187331d to
160ba86
Compare
|
/azp run |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
Why I did it
DPU reboot-cause entries written to
CHASSIS_STATE_DBwere missing theboot_idanddevicefields, so consumers couldn't correlate a DPU reboot with its boot instance orsource device. NPU entries are unaffected.
Work item tracking
How I did it
NPU_REBOOT_CAUSE_DB_FIELDS(cause, time, user, comment) andDPU_REBOOT_CAUSE_DB_FIELDS(adds boot_id, device) inprocess-reboot-cause.db.setcalls with a loop over the field setselected by device type, so DPU rows now include
boot_idanddevice.sequence warnings without changing its matching behavior.
How to verify it
tests/process-reboot-cause_test.pynow asserts that a DPUreboot-cause file results in
boot_idanddevicebeing written toCHASSIS_STATE_DB.Which release branch to backport (provide reason below if selected)
Description for the changelog
Save boot_id and device fields for DPU reboot-cause entries